Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); ARROW-17643: [R] Latest duckdb release is causing test failure by paleolimbot · Pull Request #14149 · apache/arrow · GitHub
Skip to content

ARROW-17643: [R] Latest duckdb release is causing test failure - #14149

Merged
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2
Sep 16, 2022
Merged

ARROW-17643: [R] Latest duckdb release is causing test failure#14149
nealrichardson merged 1 commit into
apache:masterfrom
paleolimbot:r-duckdb2

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@nealrichardson
nealrichardson merged commit 6926672 into apache:masterSep 16, 2022
@paleolimbot
paleolimbot deleted the r-duckdb2 branch September 16, 2022 14:23
@ursabot

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = b48d228 and contender = 6926672. 6926672 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Finished ⬇️0.27% ⬆️0.03%] test-mac-arm
[Failed ⬇️0.28% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.14% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 69266721 ec2-t3-xlarge-us-east-2
[Finished] 69266721 test-mac-arm
[Failed] 69266721 ursa-i9-9960x
[Finished] 69266721 ursa-thinkcentre-m75q
[Finished] b48d2287 ec2-t3-xlarge-us-east-2
[Finished] b48d2287 test-mac-arm
[Failed] b48d2287 ursa-i9-9960x
[Finished] b48d2287 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

@ursabot

Copy link
Copy Markdown

['Python', 'R'] benchmarks have high level of regressions.
test-mac-arm
ursa-i9-9960x

@pitrou

Copy link
Copy Markdown
Member

Is this actually fixed upstream? I see a build using DuckDB 0.5.1 here and it has the error:
https://github.com/apache/arrow/actions/runs/3095675589/jobs/5010340520#step:7:31839

@paleolimbot

Copy link
Copy Markdown
MemberAuthor

It looks like no! t I made ARROW-17809 and will look into it today and tomorrow.

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…e#14149)
apache#14065 experimented with ways to solve this from Arrow's end; however, the fix in duckdb/duckdb#4712 is probably more robust. Even if that fix doesn't make it in to the next DuckDB release, when that happens this test will start failing again in case we/I forget to check.
Authored-by: Dewey Dunnington <dewey@fishandwhistle.net>
Signed-off-by: Neal Richardson <neal.p.richardson@gmail.com>
Sign up for freeto 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.

4 participants

@paleolimbot@ursabot@pitrou@nealrichardson