[
https://issues.apache.org/jira/browse/FLINK-33903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18076441#comment-18076441
]
Sergey Nuyanzin edited comment on FLINK-33903 at 4/27/26 4:34 AM:
------------------------------------------------------------------
For now a user created in gha in template ci
Merged as
[1719376d1e97b74f45ea6f3a5ca17bb0b138080a|https://github.com/apache/flink/commit/1719376d1e97b74f45ea6f3a5ca17bb0b138080a]
2.0:
[c05a038fb9bd8259c50d0d662f4773caa7665a80|https://github.com/apache/flink/commit/c05a038fb9bd8259c50d0d662f4773caa7665a80]
2.1:
[ceeb97e0fec6ee564c3d52716498cc97db25358c|https://github.com/apache/flink/commit/ceeb97e0fec6ee564c3d52716498cc97db25358c]
2.2:
[e0b566f8a1356743461d3403e770b2ab6e7c5a5a|https://github.com/apache/flink/commit/e0b566f8a1356743461d3403e770b2ab6e7c5a5a]
2.3:
[d66a73531ee9c26b1b5f8172c8adf9655acfd344|https://github.com/apache/flink/commit/d66a73531ee9c26b1b5f8172c8adf9655acfd344]
was (Author: sergey nuyanzin):
Merged as
[1719376d1e97b74f45ea6f3a5ca17bb0b138080a|https://github.com/apache/flink/commit/1719376d1e97b74f45ea6f3a5ca17bb0b138080a]
2.0:
[c05a038fb9bd8259c50d0d662f4773caa7665a80|https://github.com/apache/flink/commit/c05a038fb9bd8259c50d0d662f4773caa7665a80]
2.1:
[ceeb97e0fec6ee564c3d52716498cc97db25358c|https://github.com/apache/flink/commit/ceeb97e0fec6ee564c3d52716498cc97db25358c]
2.2:[e0b566f8a1356743461d3403e770b2ab6e7c5a5a|https://github.com/apache/flink/commit/e0b566f8a1356743461d3403e770b2ab6e7c5a5a]
> Reenable tests that edit file permissions
> -----------------------------------------
>
> Key: FLINK-33903
> URL: https://issues.apache.org/jira/browse/FLINK-33903
> Project: Flink
> Issue Type: Sub-task
> Components: Build System / CI
> Affects Versions: 1.18.0, 1.19.0
> Reporter: Matthias Pohl
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: github-actions, pull-request-available
> Fix For: 2.4.0
>
>
> In GitHub Actions the permissions seem to work differently to how it works in
> Azure CI. In both cases, we run the test suite as root. But in GHA runners,
> the file permission changes won't have any effects because the test started
> as a root user have permissions to adapt the files in any case.
> This issue is about enabling the tests again by rewriting the tests (ideally,
> because we shouldn't rely on OS features in the tests). Alternatively, we
> find a way to make those tests work in GHA as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
