You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be worthwhile to include a build script for a non-trivial code in the documentation as another real-world example. Trilinos would be worthwhile, because building Trilinos was what originally motivated the automation framework that eventually begat staged-script. The Trilinos CI testing is primarily driven by PullRequestLinuxDriverTest.py, so we'd have to see if it's possible to mimic what's being done there, without access to Trilinos' machines, environments, etc.
The text was updated successfully, but these errors were encountered:
I'm afraid PullRequestLinuxDriverTest.py is more of a complicated mess than when I last saw it ~4 years ago, so it would take quite some time to translate into a "one build script to rule them all". I asked if there was a straightforward way to reproduce CI testing failures locally, and was pointed to these instructions, though I'm not sure that helps much.
It'd be worthwhile to include a build script for a non-trivial code in the documentation as another real-world example. Trilinos would be worthwhile, because building Trilinos was what originally motivated the automation framework that eventually begat
staged-script
. The Trilinos CI testing is primarily driven byPullRequestLinuxDriverTest.py
, so we'd have to see if it's possible to mimic what's being done there, without access to Trilinos' machines, environments, etc.The text was updated successfully, but these errors were encountered: