Taskgraph fails with non-standard root dir #522
Labels
bug
Something isn't working
Comments
ahal
added a commit
to ahal/neqo
that referenced
this issue
Jun 18, 2024
While we'd like to keep the CI configuration files hidden in this repo, I came across a bug in Taskgraph triggered by changing the root Taskgraph directory to a non standard location. This bug will require a new release to fix (and I suspect there will be other bugs revealed afterwards). In the meantime, we can move the files to the standard place while this is fixed. I filed taskcluster/taskgraph#522 to track the fix.
github-merge-queue bot
pushed a commit
to mozilla/neqo
that referenced
this issue
Jul 1, 2024
* ci: rename .taskcluster to taskcluster While we'd like to keep the CI configuration files hidden in this repo, I came across a bug in Taskgraph triggered by changing the root Taskgraph directory to a non standard location. This bug will require a new release to fix (and I suspect there will be other bugs revealed afterwards). In the meantime, we can move the files to the standard place while this is fixed. I filed taskcluster/taskgraph#522 to track the fix. * ci: use Decision docker image with Taskgraph included * ci: re-enable Taskcluster
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Taskgraph supports a
--rootflag which supposedly allows you to place the Taskgraph files into an arbitrary directory. However, due to this check:https://github.com/taskcluster/taskgraph/blob/main/src/taskgraph/config.py#L130
Doing so results in a guaranteed exception. I'd be shocked if this were the only issue. We should either support this use case or remove the flag. This came up in https://github.com/mozilla/neqo because @larseggert would like to keep the CI files in the
.taskcluster/dir to help keep them hidden from the rest of the repo files.The text was updated successfully, but these errors were encountered: