Skip to content

Add e4s_testsuite tutorial section#1368

Merged
shahzebsiddiqui merged 16 commits intobuildtesters:develfrom
wspear:patch-2
Feb 6, 2023
Merged

Add e4s_testsuite tutorial section#1368
shahzebsiddiqui merged 16 commits intobuildtesters:develfrom
wspear:patch-2

Conversation

@wspear
Copy link
Contributor

@wspear wspear commented Feb 3, 2023

No description provided.

@shahzebsiddiqui
Copy link
Member

Please fix document ci check it's not building

@wspear
Copy link
Contributor Author

wspear commented Feb 3, 2023

Please fix document ci check it's not building
@shahzebsiddiqui I think we might have a chicken egg problem. I couldn't find any formatting errors reported in the readthedocs build but it looks like the data files I added aren't in the image readthedocs uses for its build yet.

/checkouts/1368/docs/buildspecs/e4s_testsuite.rst:36: WARNING: Include file '/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/examples/spack/e4s_testsuite_mpich.yml' not found or reading it failed
WARNING: Unexpected return code 1 from command Command(command=('cat', 'buildtest_tutorial_examples/spack/build/e4s_testuite_mpich.txt'), shell=False, hide_standard_error=False, working_directory='/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs') (output='cat: buildtest_tutorial_examples/spack/build/e4s_testuite_mpich.txt: No such file or directory')
WARNING: Unexpected return code 1 from command Command(command=('cat', 'buildtest_tutorial_examples/spack/inspect/e4s_testuite_mpich.yml'), shell=False, hide_standard_error=False, working_directory='/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs') (output='cat: buildtest_tutorial_examples/spack/inspect/e4s_testuite_mpich.yml: No such file or directory')
/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs/buildspecs/spack.rst:6: WARNING: duplicate label buildtest_spack_integration, other instance in /home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs/buildspecs/e4s_testsuite.rst
looking for now-outdated files... none found

@shahzebsiddiqui
Copy link
Member

@jscook2345 can you please help review Wyatt PR, adding additional eyes can help

@shahzebsiddiqui
Copy link
Member

Please fix document ci check it's not building
@shahzebsiddiqui I think we might have a chicken egg problem. I couldn't find any formatting errors reported in the readthedocs build but it looks like the data files I added aren't in the image readthedocs uses for its build yet.

/checkouts/1368/docs/buildspecs/e4s_testsuite.rst:36: WARNING: Include file '/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/examples/spack/e4s_testsuite_mpich.yml' not found or reading it failed
WARNING: Unexpected return code 1 from command Command(command=('cat', 'buildtest_tutorial_examples/spack/build/e4s_testuite_mpich.txt'), shell=False, hide_standard_error=False, working_directory='/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs') (output='cat: buildtest_tutorial_examples/spack/build/e4s_testuite_mpich.txt: No such file or directory')
WARNING: Unexpected return code 1 from command Command(command=('cat', 'buildtest_tutorial_examples/spack/inspect/e4s_testuite_mpich.yml'), shell=False, hide_standard_error=False, working_directory='/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs') (output='cat: buildtest_tutorial_examples/spack/inspect/e4s_testuite_mpich.yml: No such file or directory')
/home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs/buildspecs/spack.rst:6: WARNING: duplicate label buildtest_spack_integration, other instance in /home/docs/checkouts/readthedocs.org/user_builds/buildtest/checkouts/1368/docs/buildspecs/e4s_testsuite.rst
looking for now-outdated files... none found

Is the test getting a nonzero return code?

@shahzebsiddiqui
Copy link
Member

Can you add test to

commands_to_run = {
that way it's automatic generated as pose to copying the output.

Next in container run buildtest tutorial-examples see https://buildtest.readthedocs.io/en/devel/contributing/build_documentation.html#generating-documentation-examples-for-buildtest-tutorial

Note you need to volume mount buildtest into container it's provided in docs.

You will see lots of files change which is expected

@codecov
Copy link

codecov bot commented Feb 3, 2023

Codecov Report

Base: 72.76% // Head: 69.46% // Decreases project coverage by -3.30% ⚠️

Coverage data is based on head (f544d4a) compared to base (8f0a9c8).
Patch coverage: 3.42% of modified lines in pull request are covered.

❗ Current head f544d4a differs from pull request most recent head 58a0fa6. Consider uploading reports for the commit 58a0fa6 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##            devel    #1368      +/-   ##
==========================================
- Coverage   72.76%   69.46%   -3.30%     
==========================================
  Files          57       57              
  Lines        6160     6277     +117     
  Branches     1066     1112      +46     
==========================================
- Hits         4482     4360     -122     
- Misses       1678     1915     +237     
- Partials        0        2       +2     
Impacted Files Coverage Δ
buildtest/builders/base.py 55.75% <0.00%> (-1.00%) ⬇️
buildtest/buildsystem/checks.py 6.03% <3.68%> (-0.96%) ⬇️
buildtest/cli/compilers.py 27.59% <0.00%> (-46.80%) ⬇️
buildtest/system.py 54.50% <0.00%> (-15.50%) ⬇️
buildtest/cli/cdash.py 88.61% <0.00%> (-0.99%) ⬇️
buildtest/config.py 49.75% <0.00%> (-0.25%) ⬇️
buildtest/executors/cobalt.py 22.11% <0.00%> (-0.24%) ⬇️
buildtest/executors/setup.py 72.95% <0.00%> (+0.13%) ⬆️
buildtest/cli/report.py 90.59% <0.00%> (+0.27%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@wspear
Copy link
Contributor Author

wspear commented Feb 4, 2023

The container example build worked for my new stuff. Here's the PR render for quick review: https://buildtest--1368.org.readthedocs.build/en/1368/buildspecs/e4s_testsuite.html

The compilers/steam_example_metrics.yml buildspec failed so I didn't recommit the other rebuilt example output. I didn't see why it was invalid at a glance and as far as I can tell the error didn't occur in the github build.

Valid Buildspecs: 0
Invalid Buildspecs: 1
/home/spack/buildtest/examples/compilers/stream_example_metrics.yml: INVALID

buildtest is unable to create any tests because there are no valid buildspecs. 

I don't think the container build error came from this commit either:

#14 exporting to image
#14 pushing layers 0.6s done
#14 ERROR: failed to push ghcr.io/buildtesters/buildtest_spack:latest: unexpected status: 403 Forbidden
------
 > exporting to image:
------
ERROR: failed to solve: failed to push ghcr.io/buildtesters/buildtest_spack:latest: unexpected status: 403 Forbidden
Error: buildx failed with: ERROR: failed to solve: failed to push ghcr.io/buildtesters/buildtest_spack:latest: unexpected status: 403 Forbidden

@shahzebsiddiqui
Copy link
Member

ok @wspear thanks for headsup, ill try to fix the error for compilers/stream_example_metrics.yml in a separate PR. Yes you dont need to commit all the example diff since it is going to be a really big commit diff. What you did was correct, only commit the changes relevant to e4s testsuite

Comment on lines +10 to +11
E4S is a spack based software stack but because not all spack packages provide internal testing functionality it
is useful to have an alternative framework for testing deployed software.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this sentence can be removed, we don't need to explain to user why we need an alternative framework for testing spack packages.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, this question comes up a lot in discussions about Spack Tests/E4S Testsuite.

@shahzebsiddiqui shahzebsiddiqui merged commit 1e29c8f into buildtesters:devel Feb 6, 2023
@shahzebsiddiqui
Copy link
Member

Congratulations @wspear on your first contribution 👏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants